Instead of relying on a centralized control plane for edge infrastructure, we propose to use independent OpenStack clouds that collaborate if needed. An approach that enables the segregation of the infrastructure into distinct areas resolving network partitioning and scalability challenges in most cases.

The main idea consists in extending the OpenStack CLI to define the collaboration process. A dedicated option, called --scope, specifies which services (e.g., compute, image) of which OpenStack clouds (e.g., Cloud1, Cloud2) an OpenStack is made of to perform the CLI request. For instance, the provisioning of a VM in Cloud1 with an image in Cloud2 looks like as follows:

openstack server create vm --flavor tiny --image cirros \
--scope '{"compute": "Cloud1", "image": "Cloud2"}'

First, we will explain the limitations of a centralized control plane. Then, we will present the --scope proposal and its proof-of-concept: a simple proxy in front of OpenStack clouds.

The videos from the Summit keynotes are now available!

Search Result

Schedule Matches

Speaker Matches

Registration Opening Soon